feat(kibana): allow supplying xpack encryption keys#160
Conversation
|
Warning Review limit reached
More reviews will be available in 30 minutes and 13 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The role generates random xpack.security.encryptionKey and xpack.encryptedSavedObjects.encryptionKey on first run. When migrating Kibana to a new host or running multiple instances these must match the existing keys, otherwise encrypted saved objects (alerting rules, connectors, Fleet tokens) and session state cannot be decrypted by the new instance. Add kibana_security_encryptionkey and kibana_encryptedsavedobjects_encryptionkey to supply them; empty keeps the generate-random default. Covered by the kibana_custom molecule scenario.
Oddly
force-pushed
the
feat/kibana-encryption-keys
branch
from
e2d61c3 to
e136cdf
Compare
1 participant
The kibana role generates random
xpack.security.encryptionKeyandxpack.encryptedSavedObjects.encryptionKeyon first run.When migrating Kibana to a new host or running multiple instances, these keys must match the existing ones. Otherwise encrypted saved objects (alerting rules, connectors, Fleet tokens) and session state cannot be decrypted by the new instance.
This adds
kibana_security_encryptionkeyandkibana_encryptedsavedobjects_encryptionkeyto supply the keys (written to the keystore via the existing flow). Both default to empty, preserving the generate-random behaviour, so there is no change for existing users. Thekibana_custommolecule scenario sets both and asserts the provided values are stored in the keystore.